System and method for direct transfer of electronic parking meter data

ABSTRACT

A single space electronic parking meter mechanism for inserting into an outer parking meter housing is provided. The mechanism includes an inner housing, a payment receiving structure supported by the inner housing and an electronic display screen supported by the inner housing. The mechanism also includes a wireless communication subsystem supported by the inner housing configured to wirelessly communicate with a parking management system and an electronic meter control system controlling the electronic display and the wireless communications subsystem. The mechanism includes a memory device receiving port externally accessible through the inner housing and a read-write removable memory device physically accessible from outside of the inner housing and configured to be coupled to the memory device receiving port. The removable memory device including operation mode information that is read by the electronic meter control system to select an operation mode of the meter mechanism.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

This application is a continuation of International Application No.PCT/US2012/037205 titled “SYSTEM AND METHOD FOR DIRECT TRANSFER OFELECTRONIC PARKING METER DATA,” filed May 10, 2012, which claims thebenefit of U.S. Provisional Patent Application No. 61/484,568 titled“PARKING METER SYSTEMS AND METHODS,” filed May 10, 2011. InternationalApplication No. PCT/US2012/037205 and U.S. Provisional PatentApplication No. 61/484,568 are incorporated herein by reference in theirentireties.

BACKGROUND OF THE INVENTION

The present invention relates generally to the field of parking metersystems, devices and methods. The present invention relates specificallyto a parking meter system equipped for replacement of meter mechanism ofparking meters within the system.

Single space parking meters are typically associated with a singleparking space. To utilize an individually metered parking space, amotorist typically inserts money into the parking meter, and the parkingmeter displays an amount of time related to the amount of moneyinserted. A multi-space meter typically provides a single paymentlocation for more than one parking spot, and the multi-space meterreceives payment and tracks meter time for the multiple parking spots.For either type of meter, the motorist may park at the metered spot forthe amount of parking time purchased. When the time on the meterexpires, the motorist may move their car or add more time to the meter.If the meter expires and the motorist remains parked at the meter, aparking enforcement officer may issue a parking ticket. A city or otherentity may operate a city wide system of single space parking metersand/or multi-space meters.

SUMMARY OF THE INVENTION

Generally, one embodiment of the invention relates to a single spaceparking meter mechanism with a removable memory device port. The metermechanism is configured to select an operating mode based upon modeoperation information read from a removable memory device received inthe port. Another embodiment of the invention relates to a method ofdirectly transferring data from a pre-existing single space metermechanism to a new single space meter mechanism during replacement ofthe pre-existing single space meter mechanism.

Another embodiment of the invention relates to a single space electronicparking meter mechanism for inserting into an outer parking meterhousing. The single space electronic parking meter mechanism includes aninner housing, a payment receiving structure supported by the innerhousing, an electronic display screen supported by the inner housing, awireless communication subsystem supported by the inner housingconfigured to wirelessly communicate with a parking management system,an electronic meter control system controlling the electronic displayand the wireless communications subsystem, a memory device receivingport externally accessible through the inner housing and a read-writeremovable memory device physically accessible from outside of the innerhousing and configured to be coupled to the memory device receivingport. The removable memory device including operation mode informationthat is read by the electronic meter control system to select anoperation mode of the meter mechanism.

Another embodiment of the invention relates to a single space parkingmeter kit including a first single space meter mechanism and a secondsingle space meter mechanism. The first single space meter mechanismincludes an inner housing, an electronic display screen supported by theinner housing of the first single space meter mechanism, a wirelesscommunication subsystem supported by the inner housing of the firstsingle space meter mechanism configured to wirelessly communicate with aparking management system, an electronic meter control systemcontrolling the electronic display and the wireless communicationssubsystem of the first single space meter mechanism and a removableread-write memory device accessible from outside of the inner housing ofthe first single space meter mechanism. The removable memory deviceincluding location identification information representative of thephysical, geographic location of the first single space meter mechanismwithin a parking system. The second single space meter mechanismincludes an inner housing, an electronic display screen supported by theinner housing of the second single space meter mechanism, a wirelesscommunication subsystem supported by the inner housing of the secondsingle space meter mechanism configured to wirelessly communicate withthe parking management system, an electronic meter control systemcontrolling the electronic display and the wireless communicationssubsystem of the second single space meter mechanism, a meteridentification number, and a port configured to receive the removableread-write memory device. The control system of the second single spacemeter mechanism is configured to access the location identificationinformation from the removable read-write memory device and tocommunicate both the location identification information and the meteridentification number of the second single space meter to the parkingmanagement system.

Another embodiment of the invention relates to a computerized parkingmanagement system for processing, storing and communicating data withina wirelessly communicating parking system, and the parking systemincludes a plurality of single-space parking meters each equipped withan electronic meter mechanism. The parking management system includes acontrol computer and a parking system database controlled by the controlcomputer. The database includes a unique meter ID representative of eachelectronic meter mechanism within the parking system and a uniquelocation ID representative of the physical, geographic location of eachsingle-space parking meter within the parking system. The parkingmanagement system includes wireless communications hardware controlledby the control computer to transmit data wirelessly to the plurality ofsingle space parking meters within the parking system. Followingreplacement of a pre-existing electronic meter mechanism with a newelectronic meter mechanism at one of the single space parking meters,the control computer is configured to receive a new meter IDcommunicated wirelessly from the new meter mechanism that identifies thenew electronic meter mechanism. The control computer is configured toassociate the new meter ID with the location ID for the single spacemeter that has received the new electronic meter mechanism within theparking system database.

Another embodiment of the invention relates to a method of replacing apre-existing electronic meter mechanism with a new electronic metermechanism. The method includes opening an outer meter housing thatsurrounds the pre-existing electronic meter mechanism. The methodincludes directly transferring location ID information representative ofthe physical, geographic location of the outer meter housing from thepre-existing electronic meter mechanism to a memory device physicallyassociated with the new electronic meter mechanism. The method includestransmitting the location ID information wirelessly from the new metermechanism to a parking management system.

Another embodiment of the invention relates to a method of replacing apre-existing electronic meter mechanism with a new electronic metermechanism. The method includes delivering a new meter mechanism to arecipient. The new meter mechanism including an inner housing, anelectronic display screen supported by the inner housing, a wirelesscommunication subsystem supported by the inner housing configured towirelessly communicate with a parking management system, an electronicmeter control system controlling the electronic display and the wirelesscommunications subsystem and a port configured to receive data directlyfrom the pre-existing meter mechanism. The method includes the recipientof the new meter mechanism opening an outer meter housing that surroundsthe pre-existing electronic meter mechanism and directly transferringlocation ID information representative of the physical, geographiclocation of the outer meter housing from the pre-existing electronicmeter mechanism to the new electronic meter mechanism. The new metermechanism is configured to transmit the location ID informationwirelessly directly from the new meter mechanism to the parkingmanagement system.

Alternative exemplary embodiments relate to other features andcombinations of features as may be generally recited in the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

This application will become more fully understood from the followingdetailed description, taken in conjunction with the accompanyingfigures, wherein like reference numerals refer to like elements inwhich:

FIG. 1 shows a parking system according to an exemplary embodiment.

FIG. 2 shows a parking system according to another exemplary embodiment.

FIG. 3 shows a parking system according to another exemplary embodiment.

FIG. 4 is a block diagram of a parking system according to an exemplaryembodiment.

FIG. 5 is a front view of a single-space parking meter according to anexemplary embodiment.

FIG. 6 is an exploded view of a single-space parking meter according toan exemplary embodiment.

FIG. 7 is a front perspective view of an electronic meter mechanismaccording to an exemplary embodiment.

FIG. 8 is front perspective view of an electronic meter mechanism and aremovable memory device according to an exemplary embodiment.

FIG. 9 is a front perspective view of the electronic meter mechanism ofFIG. 8 showing the memory device removed according to an exemplaryembodiment.

FIG. 10 is a diagram depicting a removable memory device according to anexemplary embodiment.

FIG. 11 is a flow diagram showing replacement of a pre-existing metermechanism with a new, replacement meter mechanism according to anexemplary embodiment.

FIG. 12 is a flow diagram showing use of the removable memory device ofFIG. 10 by the controller of the new, replacement meter mechanismaccording to an exemplary embodiment.

FIG. 13 is a diagram depicting a removable memory device configured fordiagnostics and maintenance according to an exemplary embodiment.

FIG. 14 is a flow diagram showing use of the removable memory device ofFIG. 13 by the controller of an electronic meter mechanism according toan exemplary embodiment.

FIG. 15 is a diagram depicting a removable memory device configured forassigning an electronic meter mechanism to a low power storage modeaccording to an exemplary embodiment.

FIG. 16 is a flow diagram showing use of the removable memory device ofFIG. 15 by the controller of an electronic meter mechanism according toan exemplary embodiment.

FIG. 17 is a diagram depicting a removable memory device configured fordata extraction according to an exemplary embodiment.

FIG. 18 is a flow diagram showing use of the removable memory device ofFIG. 17 by the controller of an electronic meter mechanism according toan exemplary embodiment.

FIG. 19 is a block diagram showing an electronic meter mechanismaccording to an exemplary embodiment.

FIG. 20 is a block diagram of a controller for a parking meter accordingto an exemplary embodiment.

DETAILED DESCRIPTION

Before turning to the figures, which illustrate the exemplaryembodiments in detail, it should be understood that the presentapplication is not limited to the details or methodology set forth inthe description or illustrated in the figures. It should also beunderstood that the terminology is for the purpose of description onlyand should not be regarded as limiting.

Referring generally to the figures, various embodiments of a wirelesslycommunicating single space parking meter, a parking system utilizingsuch parking meters and related methods are disclosed herein. Generally,the single space meters discussed herein include an electronic metermechanism that includes various electronic devices (e.g., wirelesscommunication equipment, multifunctional electronic display, variouspayment devices, vehicle sensor, power supply, and/or controlelectronics, etc.). Typically, the electronic meter mechanism is locatedwithin an outer housing when in use.

Under certain conditions (e.g., upgrade, replacement, etc.), a newelectronic meter mechanism may be swapped out for the current metermechanism located within the outer meter housing. The variousembodiments of the electronic single space meter mechanism discussedherein include a removable read-write memory device that stores meterand location specific information. To replace the current meter with thenew meter, the removable memory device is removed from the current meterand plugged into the new meter. The new meter reads the information fromthe removable memory device, and utilizes the information to associatethe new meter with the particular physical location within the parkingsystem. In various embodiments, the removable memory device may includeall of the information needed to assign the new meter to the locationand to allow the meter to operate properly in the new location. Further,in some embodiments, different versions of a read-write removable memorydevice may be used to provide additional functionality discussed herein.

Referring to FIGS. 1, 2 and 3, various exemplary embodiments of parkingsystem 10 are shown. In the exemplary embodiment of FIG. 1, parkingsystem 10 includes one or more single-space parking meters 12, one ormore multi-space parking meters 14, a communication network, shown aswireless network 16, and a parking system control system, shown asparking management system 18. Both single-space meters 12 andmulti-space meter 14 may be configured to communicate with parkingmanagement system 18 by directly accessing wireless network 16. Invarious embodiments, wireless network 16 may be a mobile telephonesystem, and meters 12 and 14 may access wireless network 16 utilizingstandard mobile telephone systems (e.g., GSM, GPRS, EDGE, etc.).

As discussed in more detail below, meters 12 and 14 are configured tocommunicate parking meter data to parking management system 18 viawireless network 16. Parking management system 18 is a computerized,server system that includes a parking database that provides forprocessing, storage and management of data within parking system 10. Inone embodiment shown in FIG. 1, parking management system 18 includes atleast one server 19 and wireless communications subsystem 21. Server 19is configured to store and process parking data associated with aparticular parking spot (e.g., current parking space occupancyinformation, current meter time, vehicle sensor data, informationregarding mode of payment, vehicle arrival information, vehicledeparture information, parking rates, location information, etc.),including parking data received wirelessly from the meters, to generallyprovide the parking system functions discussed herein. Wirelesscommunications hardware 21 of parking management system 18 is configuredto allow server 19 to communicate wirelessly with the various componentsof parking system 10 discussed herein.

Server 19 is configured to store and generate data that may becommunicated wirelessly to the various components of parking system 10,and in this embodiment, wireless communication hardware 21 is configuredto transmit system data or information from server 19 to the appropriatecomponent of the parking system. For example, wireless communicationhardware 21 is configured to transmit and meters 12 and 14 areconfigured to receive information from parking management system 18 viawireless network 16. The system data transmitted from parking managementsystem 18 and received by the parking meters 12 and 14 may includeparking meter configuration data, parking rate data, time and date data,testing and diagnostic data, parking meter software updates, etc. Itshould be understood that while the embodiments discussed herein relateprimarily to a parking system that communicates with parking managementsystem 18 via a wireless communication network 16, in other embodiments,a wired or a combination wired/wireless communication network may beused to provide communication to parking management system 18.

Server 19 is also configured to manage and track information related tothe particular devices associated with parking system 10. In oneembodiment, server 19 includes one or more control computes and aparking system database. The database maintained by server 19 tracks theserial number or other unique identifier of each electronic metermechanism associated with each single space meter 12 within parkingsystem 10. In this embodiment, the database associates electronic metermechanism serial number (or other meter identification data) with aunique location identifier (e.g., location ID 130 discussed below) thatidentifies the physical, geographic location of the single space meterthat is equipped with the electronic meter mechanism. The databasestored on server 19 also stores other information tied to a particularsingle space meter. For example, the database stores rate information,configuration data, software and firmware version information associatedwith the unique location identifier that identifies the physical,geographic location of the single space meter that is equipped with theelectronic meter mechanism. This data may be provided wirelessly to theelectronic meter mechanism as needed to ensure the electronic metermechanism is up to date. In addition, after a new electronic metermechanism is installed into a single space meter as discussed below, thenew meter mechanism may synchronize itself with the database to ensurethe data the new meter mechanism has for the particular location ID iscorrect and up to date. In one such embodiment, following replacement ofa pre-existing electronic meter mechanism with a new electronic metermechanism at one of the single space parking meters, server 19 isconfigured to receive the serial number (or other unique meteridentifier) communicated wirelessly from the new meter mechanism thatidentifies the new meter mechanism. When the new meter identificationinfo is received, the control computer is configured to modify theparking system database to associate the new meter identification infowith the location ID for the single space meter that received the newmeter mechanism.

Parking system 10 also includes one or more vehicle sensors, shown aspole-mount vehicle sensors 20, curb surface-mount sensor 22 and streetsurface-mount sensor 24. Generally, sensors 20, 22 and 24 are eachassociated with a single parking space 26 and are configured to detectthe presence of a vehicle located in the associated parking space, todetect entry of a vehicle into the associated parking space and/or todetect the exit of a vehicle from the associated parking space. In theembodiment of FIG. 1, a pole-mount sensor 20 is associated with and incommunication with each single-space meter 12, and sensors 22 and 24 areassociated with and in communication with multi-space meter 14. In otherembodiments, a subterranean sensor may be located beneath the surface ofthe parking spot in place of street surface-mount sensor 24. In otherembodiments, a curb surface-mount sensor 22, a street surface-mountsensor 24 or subterranean sensor, may be associated with a single-spacemeter 12 instead of pole-mount sensor 20. Generally, vehicle sensors 20,22 and 24 are directional sensors (i.e., sensor that only senses in aparticular region or direction) and include a targetable detection zone.Generally, the vehicle sensors are positioned such that the targetabledetection zone is located within the parking space associated with themeter and is not located in adjacent parking spaces.

Vehicle sensors 20, 22 and 24 are configured to detect one or moreaspect (e.g., presence, entry, exit, etc.) of a vehicle within theparking spot associated with the sensor and to generate a signalindicative of the detected aspect of the vehicle. The generated signalis then communicated from the sensor to a controller associated with theparking meter for the parking spot. In various embodiments,communication from the sensors to the associated meter may be eitherthrough wired or wireless communication. The parking meter may executevarious functions (e.g., update time on the meter, restrict furtherparking in the space, determine the meter is expired, etc.) in responseto the detected aspect of the vehicle and may send data to and/orreceive data from parking management system 18 in response to thedetected aspect of the vehicle. In addition, data generated by thevehicle sensor associated with each meter (e.g., data related to thepresence of a vehicle within the space associated with the meter) may becommunicated to parking management system 18 via the wirelesscommunications hardware of the meter.

Referring to FIGS. 1, 2 and 3, parking system 10 includes a plurality ofsingle-space meters 12 (e.g., 2, 3, 4, . . . 50, . . . 100, more than 2,more than 10, more than 20, more than 50, more than 100, etc.,single-space meters), and may include one or more multi-space parkingmeters 14. In such embodiments, the database maintained by server 19includes a unique location identifier associated with each of the meterswithin parking system 10.

In the embodiments shown, each single-space parking meter 12 includes apole mounted vehicle sensor 20 physically coupled to and supported bythe parking meter pole 75. As shown, pole 75 includes a lower endcoupled to the ground adjacent to and set back from parking space 26associated with the meter 12 such that there is a distance or spacelocated between pole 75 and space 26. With vehicle sensor 20 coupled topole 75, a space is present between vehicle sensor 20 and parking space26, and vehicle sensor 20 is configured to detect an aspect of a vehiclelocated within parking space 26 across the space. As shown in FIG. 1,vehicle sensor 20 includes a targetable detection zone 30, and vehiclesensor 20 is positioned on pole 75 such that the detection zone 30 ofvehicle sensor 20 is located within parking space 26. In anotherembodiment, vehicle sensor 20 may be physically coupled to and supportedby the parking meter housing. In these embodiments, vehicle sensor 20 islocated above both the street and sidewalk surface and is also set backfrom the curb.

Referring to FIGS. 1 and 3, in various embodiments, parking system 10may also include curb mount vehicle sensors 22 and/or street mountvehicle sensors 24 that communicate parking space usage informationwirelessly to a multi-space meter 14 or directly to parking managementsystem 18. In contrast to pole-mount sensors 20, curb mount vehiclesensors 22 and/or street mount vehicle sensors 24 include their ownpower supply and communications hardware. In the embodiment shown inFIG. 1, curb mount vehicle sensors 22 and/or street mount vehiclesensors 24 are stand-alone sensors configured for relatively short rangewireless communication to a multi-space meter 14, and multi-space meter14 is configured for cellular communication with parking managementsystem 18.

Generally, the vehicle sensors include a sensing element (e.g., anelectromagnetic energy transmitter and receiver, transceiver, etc.)located within sensors housing. Sensors 20, 22 and 24 may be sensorsconfigured to utilize electromagnetic energy to detect the presence ofthe vehicle in the parking space, and specifically, sensors 20, 22 and24 may be a radiofrequency (RF) sensor including a radiofrequency-basedsensing element. In other embodiments, sensors 20, 22 and 24 may be anysensors suitable for detecting an aspect of a vehicle in the associatedparking space. For example, sensors 20, 22 and 24 may be infraredreflectance sensors, ultrasonic sensors, capacitance sensors, proximitysensors, magnetic sensors, magnetic-flux sensors, non-intrusive sensors,radar-based sensors, a low power/broad spectrum radar sensor, time offlight sensors, ranging sensors, etc.

In addition to generating signals indicative of vehicle presence,vehicle entry to the parking spot and vehicle exit from a parking spot,vehicle sensors 20, 22 and 24 may be configured to generate othersignals related to the parking spot or vehicles located in the parkingspot that may be used by parking system 10. For example, the vehiclesensors may be configured to generate a signal indicative of a vacantparking spot. In another embodiment, the vehicle sensors may beconfigured to generate a signal indicative of the type of vehiclelocated in the parking spot. For example, the vehicle sensor may beconfigured to generate a signal indicative of a motorcycle, a signalindicative of a car, a signal indicative of a truck, etc., being presentin parking space 26. As another example, the vehicle sensor may beconfigured to generate a signal indicative of a privately owned vehiclelocated in parking space 26 and a different signal indicative of apublicly-owned or government vehicle located in parking space 26. Inother embodiments, a vehicle sensor may include a digital cameraconfigured to capture image data of a vehicle located in the parkingspot. In one embodiment, the electronic meter mechanism associated witheach single space meter may store this vehicle sensor information whichmay be transferred to a new meter (e.g., using removable memory device64, discussed below) or may be extracted for use elsewhere (e.g., usingdata extraction memory device 300 discussed below).

Referring back to FIG. 1, parking system 10 may include one or moremobile citation units, shown as handheld unit 34. Handheld unit 34communicates with parking management system 18 via wireless network 16.In the embodiment shown in FIG. 1, handheld unit 34 includes wirelesscommunications hardware for communication with parking management system18 via wireless network 16. Handheld unit 34 is carried by parkingenforcement personnel and is used to issue citations for parkingviolations. Handheld unit 34 sends various types of enforcement data(e.g., data indicating issuance of a citation, data related to the typeof citation issued, location of parking violation, vehicleidentification information, etc.) to parking management system 18 viawireless network 16. Handheld unit 34 also receives various informationfrom parking management system 18. In one embodiment, handheld unit 34receives information to facilitate the issuances of citations. Forexample, handheld unit 34 may receive data indicative of the existenceand location of expired meters. In one embodiment, handheld unit 34 mayreceive data regarding which meters within a certain distance from unit34 are expired. It should be understood that while the figures show ahandheld citation unit, other mobile citation units may be used withinparking system 10. For example, a mobile citation unit may be mountedwithin a vehicle driven by enforcement personnel.

Referring to FIG. 2, parking system 10 is shown according to anotherexemplary embodiment. In this embodiment, parking system 10 includes aplurality of single-space meters 12 each having a pole-mounted vehiclesensor 20, a wireless network 16 and a parking management system 18.This embodiment of parking system 10 includes a gateway 36, andsingle-space meters 12 are configured for short-range communication withgateway 36. In this embodiment, gateway 36 provides the communicationlink between multiple meters 12 and parking management system 18 viawireless network 16. In one such embodiment, single-space meters 12 areconfigured for short-range RF communication with gateway 36, and gateway36 is configured for communication (e.g., cellular, WIFI, etc.) withparking management system 18 via wireless network 16. Communicationbetween meters 12 and gateway 36 may be via any suitable RFcommunication technology, standard, or protocol (e.g., WIFI, IEEE802.15.4, Bluetooth, ZigBee, etc.). Parking system 10 may also includeone or more multi-space parking meter 14 in place of, or in addition to,single-space meters 12. In such an embodiment, the multi-space meter mayalso communicate with gateway 36 using a wireless, RF technology.

Referring to FIG. 3, another embodiment of parking system 10 is shownincluding a gateway 38 and a multi-space meter 40. In this embodiment,parking system 10 includes one or more stand-alone vehicle sensors, suchas curb surface-mount sensor 22 and street surface-mount sensor 24,configured to monitor occupancy of the parking spaces associated withmulti-space meter 40. In this embodiment, gateway 38 receives wirelesscommunication from both single-space meters 12 and the stand-alonevehicle sensors (i.e., sensor 22 and sensor 24). Similar to theembodiment shown in FIG. 5, gateway 38 communicates information receivedfrom meters 12 and sensors 22 and 24 to parking management system 18 viawireless network 16. Multi-space meter 40 communicates directly withparking management system 18 via wireless network 16. In thisembodiment, parking management system 18 is configured to properlyassociate the data received from the stand-alone vehicle sensors withthe data for the appropriate parking space received from multi-spacemeter 40.

Also as shown in FIG. 3, parking system 10 may be configured to providecompatibility between parking meters made by different companies. Forexample, in one embodiment, parking meters 12 may be produced by a firstcompany or manufacturer and multi-space meter 40 may be made by a secondcompany or manufacturer. In this embodiment, sensors 20, 22 and 24 maybe compatible with meters made by different companies. Further, parkingmanagement system 18 is configured to receive, store and process datareceived from parking meters or vehicle sensors made by differentcompanies. This allows current, installed single-space and multi-spacemeters manufactured by different companies to be upgraded to provide thewireless communications and vehicle sensing functionalities discussedherein.

Referring to FIG. 4, a block diagram of parking system 10 is shownaccording to an exemplary embodiment, and includes a single-spaceelectronic parking meter 12. It should be understood that parking system10 may include a plurality of single-space parking meters 12 and one ormore multi-space meters 14 as discussed above. As shown in FIG. 4,single space meter 12 includes an outer housing 42 and an electronicmeter mechanism 44 located within outer housing 42. Electronic metermechanism 44 includes an inner housing 46 that supports the electronicsof electronic meter mechanism 44.

FIG. 4 also shows a block diagram of the components and device ofelectronic meter mechanism 44. Meter mechanism 44 includes a parkingmeter control system 50, a communication subsystem 52, a display 54, apower supply 56, a user input device 58, a payment subsystem 60, avehicle sensor 62 and a removable memory device 64. Parking metercontrol system 50 is communicably coupled to communication subsystem 52,display 54, power supply 56, user input device 58, payment subsystem 60,vehicle sensor 62 and removable memory device 64. Parking meter controlsystem 50 may generally be any electronic control unit suitable toprovide the various parking meter functionalities discussed below. Forexample control system 50 may include one or more processing circuitshaving hardware (e.g., processors, memory, communication interfaces,etc.) and/or software configured to control the operation of parkingmeter 12 as discussed herein. In one embodiment, control system 50includes two processors that each control various device of metermechanism 44, as shown in FIG. 19.

Communication subsystem 52 includes hardware and/or software forcommunicating data between parking meter control system 50 and parkingmanagement system 18 via wireless network 16. As shown in FIG. 1communication subsystem 52 may be a communication subsystem associatedwith a single-space parking meter 12 that is configured to communicatedata between the associated meter and parking management system 18 viawireless network 16 utilizing standard mobile telephone communicationsystems (e.g., GSM, GPRS, EDGE, etc.). As shown, in FIGS. 2 and 3,communication subsystem 52 may include RF communication hardware andsoftware physically coupled to single-space parking meter 12 and/orassociated with a stand-alone vehicle sensor and a gateway, such asgateway 36 and 38. In this embodiment, data is communicated fromsingle-space meter 12 or from the stand-alone vehicle sensor to thegateway and the gateway communicates the information to parkingmanagement system 18.

Single-space meter 12 also includes a display 54 that displays variousparking related information (e.g., parking rate, current time and date,time remaining on meter, a meter expired message, user operationinstructions, hours of meter operation, meter status information, userinformation during replacement, maintenance and data extractionprocesses, etc.) to the user of single-space meter 12. Display 54 may bea graphical high contrast, low power display. The display may be coloror monochrome. Display 54 may be an LED display or LCD display. In otherembodiments, display 54 includes both a front facing screen on thesidewalk facing side of the meter and a rear facing screen on the streetfacing side of the meter.

Single-space meter 12 also includes a power supply 56 suitable to powerthe functions of single-space meter 12 discussed herein. In oneembodiment, power supply 56 may include one or more solar cells or solarpanels and one or more self-sustained energy storage devices (e.g.,rechargeable batteries, ultracapacitors, etc.). In other embodiments,power supply 56 may be wired AC power supply. In one embodiment,single-space meter 12 may be configured to communicate power supply datawirelessly to parking management system 18 via the meter's wirelesscommunication hardware. Power supply data may include data related to abattery and/or solar cell of the meter (e.g., battery charge rate,remaining battery charge, remaining battery life, real-time currentsupplied by solar cell, average current supplied by solar cell,resistance at various sections within the power supply, error messagesindicating battery failure, error messages indicating solar panelfailure, real-time power consumption, average power consumption, etc.).

Single-space meter 12 also includes a user input device 58 that allowsthe user to interact with and operate the meter. In one embodiment, userinput device 58 is a four button keypad that provides tactile feedbackand/or audible feedback to the user. Single-space meter 12 also includesa payment subsystem 60 configured to receive and process payment forparking In one embodiment, payment subsystem 60 includes currency reader(e.g., a money or coin slot and a money detector, a bill slot and billdetector, etc.), a credit-card, mag-strip reader, a smart card reader,and/or a “pay by phone” system. Further, single-space meter 12 alsoincludes a vehicle sensor 62 (e.g., pole-mount vehicle sensors 20, curbsurface-mount sensor 22 and street surface-mount sensor 24 as shown inFIGS. 1, 2 and 3) that communicates information to control system 50regarding an aspect of a vehicle in the parking space associated withmeter 12.

Single space meter 12 includes a removable, read-write memory device 64.Generally, removable memory device 64 stores information and/or softwarethat can be utilized by single space meter 12 to allow single spacemeter 12 to operate properly based on the physical location of meter 12within parking system 10 and based upon the particular parking system 10(e.g., meter configurations specialized for a particular city suchdisplay of city name). Generally removable memory device 64 stores theinformation and/or software in a computer or electronics readable form.As explained in more detail below, memory device 64 may be removed froma first, current or pre-existing meter mechanism 44 located within aparticular meter housing and inserted into a socket or port on a newmeter mechanism 44 that is to replace the current meter mechanism. Thenew meter mechanism 44 reads the data from memory device 64 and utilizesthe data to program the new meter mechanism 44 to function properlybased on the physical location of meter 12 within parking system 10 andbased upon the particular parking system 10. In various embodiments, inaddition to storing information in a computer or electronics readableform, the information stored by removable memory device 64 may includehuman readable indicia (e.g., a written label, a logo, a color code,text, numbers, graphics, etc.) representative of information such as thelocation of an individual meter 12, an identification number for theouter housing of an individual meter 12, an identifying number for aparticular memory device 64, etc. The human readable indicia mayfacilitate insertion of memory device 64 into the proper meter mechanismor placement of the proper meter mechanism into the proper outer housingduring meter replacement by providing human readable indicia that thetechnician can check to ensure the proper replacements have occurred.

In various embodiments, memory device 64 may store locationidentification information representative of the physical location ofouter meter housing 42 that the new meter mechanism is being installedinto. Memory device 64 may also include payment informationrepresentative of parking payments received by the meter. For examplepayment information may include audit data indicating the amount ofcurrency that has been received by the meter and that should be locatedin the currency holder within outer meter housing 42. Paymentinformation may also include information regarding credit cardtransactions received by the meter including batched credit cardtransaction data that were not able to receive real-time credit cardauthorization. Memory device 64 may also include meter mechanismconfiguration data. Configuration data may include rate information(e.g., information indicating the parking rate and parking times thatthe rate applies), display configuration files (e.g., data that is usedby the meter mechanism controller to display the appropriate informationon the electronic display screen of the meter) and metersoftware/firmware (e.g., the appropriate software/firmware versions thatallow the meter mechanism to operate within the particular parkingsystem).

In one embodiment, memory device 64 is generally a portable, removable,read-write memory device (e.g., a serial memory device, a memory card, amemory stick, a datakey, etc.). Memory device 64 generally includes oneor more electrical contacts configured to contact mating contactslocated within meter mechanism 44. In one embodiment, memory device 64may be a serial flash memory device. In other embodiments, memory device64 may be other types of removable, read-write memory device includingfor example, CompactFlash, microSD, miniSD, USB flash, etc.

Referring to FIG. 5, single-space meter 12 is shown according to anexemplary embodiment. Single-space meter 12 includes an outer housing 42and an electronic meter mechanism 44 (shown outside of outer housing 42in FIG. 6). Outer housing 42 acts to protect electronic meter mechanism44 and includes a locking mechanism to prevent unwanted access to metermechanism 44. Outer housing 42 includes a lower housing portion 71 and acap portion 73. Cap 73 of outer housing 42 includes a transparentportion or window 74 which allows the user to view the display ofelectronic meter mechanism 44 when it is locked within outer housing 42.Lower portion 71 of outer housing 42 is coupled to an upper end of asupport structure or pole 75 that supports meter 12. Lower portion 71 ofouter housing 42 has an interior cavity 77 (shown in FIG. 6) and a front(i.e., sidewalk facing) face 76 having a payment device opening, shownas an aperture 78. To assemble meter 12, electronic meter mechanism 44is received within cavity 77 and cap 73 is coupled to lower portion 71such that electronic meter mechanism 44 is secured within housing 42.

Referring to FIG. 7, electronic meter mechanism 44 is shown outside ofmeter housing 42. Electronic meter mechanism 44 includes an innerhousing 46 that supports the various components and electronics ofelectronic meter mechanism 44. Inner housing 46 is generally the shellor structure that encases and supports the electronics of metermechanism 44. Inner housing 46 also couples to the inner surface ofouter housing 42 such that electronic meter mechanism 44 may besupported by and secured to outer housing 42. As discussed above,electronic meter mechanism 44 includes an electronic display screen,shown as display 54, which displays information to the user. In oneembodiment, display 54 includes a first screen viewable from the frontof meter mechanism 44 and a second screen viewable from the rear ofmeter mechanism 44.

Generally, meter mechanism 44 includes a payment receiving structureincluding one or more payment devices configured to receive payment froma motorist (e.g., a credit card reader, a currency reader, a smart cardreader, etc.). In addition, meter mechanism 44 includes a user inputdevice (e.g., a keypad, touch screen, buttons, switches, etc.) thatreceives inputs from the motorist in order to operate the parking meter.Typically, the payment receiving structure and the user input device islocated on the front side of the inner housing such that the motorist islocated on the sidewalk when applying payment to the meter orinteracting with the user input device.

The exemplary embodiment of electronic meter mechanism 44 shown in FIG.7 includes an integrated payment and user-interface structure 82 thatextends outward from the front side of inner housing 46. Structure 82includes both at least the physical, payment receiving components ofboth the payment subsystem 60 and the user input device 58. Structure 82is an extended portion of the housing that supports both the paymentreceiving structure and the user input device of meter mechanism 44. Inthe embodiment shown, user input device 58 is a four button interfaceincluding up and down arrow keys, an OK button and a cancel button. Inthe embodiment shown, payment subsystem 60 includes a hybrid card readerincluding both a smart card reader 84 and a credit card mag strip reader86. Payment subsystem 60 also includes a money slot, shown as coin slot88, and located within structure 82 is a currency reader that detectscurrency (coins in the example shown) that passes through coin slot 88.In other embodiments, the money slot and currency reader may beconfigured to accept and detect paper money. Smart card reader 84 may beconfigured to read a variety of smart-card type payment cards, forexample, smart-card credit cards, smart-card debit cards, proprietaryparking payment smart cards, etc. Credit card reader 86 may beconfigured to read a variety of mag-strip based payment cards, includingmag-strip credit cards, mag-strip debit cards, proprietary parkingmag-strip payment credit cards, etc. In another embodiment, paymentsubsystem 60 also includes an RF based payment system configured to readan RFID tag associated with the vehicle (e.g., iPass), and to process aparking payment to a pre-registered account associated with thevehicle's RFID tag.

Referring to FIG. 7, credit card reader 86 includes a slot 87 formed inthe front face of structure 82. Slot 87 provides the entrance thatallows a credit card to be inserted into and to be read by the mag-stripreader of credit card reader 86. As shown, slot 87 is angled relative tothe vertical axis of the front face of structure 82. In the embodimentshown, slot 87 is angled such that the upper end of the slot is locatedlaterally inward from the lower end of the slot. Slot 87 extendsdownward and laterally outward from its upper end to its lower end.Because the length of slot 87 is determined by the size of the type ofcredit card to be read, angling slot 87 allows for conservation of spaceon the front face of structure 82.

As shown in FIGS. 7 and 8, electronic meter mechanism 44 includes afront solar panel 90 that provides power to operate electronic meter 72and to charge a rechargeable battery located inside inner housing 46Inner housing 46 includes a front shelf, shown as shelf 92, upon whichfront solar panel 90 is mounted. Further, shelf 92 extends from thefront surface (i.e., the sidewalk facing surface) of inner housing 46and is positioned below (i.e., at a lower position as measured along thevertical axis of the meter mechanism) display 54 such that shelf 92 islocated below window 74 of outer housing 42. Thus, this positioning ofsolar panel 90 allows meter mechanism to be installed into apre-existing meter housing in a configuration that allows sun light toreach panel 90 after the meter mechanism is secured within outer housing42. Electronic meter mechanism may also include a rear solar panelsimilar to solar panel 90 but located on the rear (i.e., street-facingside of the meter mechanism). In other embodiments, electronic metermechanism 44 may include one solar panel or more than two solar panels.

Electronic meter mechanism 44 is configured to provide wirelesscommunication from the meter to parking management system 18. In oneembodiment, electronic meter mechanism 44 may include cellularcommunications hardware (e.g., GPRS modem, antenna, etc.) located withinand/or coupled to inner housing 46. In another embodiment, electronicmeter mechanism 44 includes RF communications hardware (e.g.,point-to-multipoint RF modem, antenna, etc.). In another embodiment,electronic meter mechanism 44 includes both cellular communicationshardware and RF communications hardware allowing the mechanism to beincorporated into either systems using a gateway or using direct metercellular communications.

Referring to FIG. 6, meter mechanism 44 is received within cavity 77 oflower housing 71. Payment-user interface structure 82 is received withinaperture 78 and extends outward from outer housing 42. This arrangementallows the motorist to interact with payment systems and the userinterface 82, when most of electronic meter mechanism is secured withinouter housings 42. Next, cap 73 is coupled to lower housing 71. FIG. 5shows meter mechanism 44 secured within housing 42 following attachmentof cap 73 to lower housing 71.

FIG. 8 shows meter mechanism 44 according to an exemplary embodiment.FIG. 8 shows removable memory device 64 received within slot 80. Slot 80is an opening or aperture that extends through inner housing 46 thatallows removable memory device 64 to engage electrical contacts of amemory device reader located inside inner housing 46. In the embodimentshown in FIG. 8, slot 80 is formed through a lateral surface of innerhousing 46. Lateral positioning of slot 80 makes slot 80 and memorydevice 64 less conspicuous to the user of meter 12, when the metermechanism is received within outer housing 42. It should be noted thatin the embodiment of FIG. 8, that interface structure 82 includes avertical key pad that is recessed within the keypad housing in contrastto the keypad shown in the embodiment of FIG. 7 that includes an angledsurface.

Referring to FIG. 9, memory device 64 includes an outer section 100 andan inner portion 102 including electrical contacts 104. When installedinto slot 80, inner portion 102 is received within inner housing 46 andelectrical contacts 104 are engaged with opposing contacts of a memorydevice reader located within slot 80. The electrical contact provided byelectrical contacts 104 allows parking meter control system 50 to readand write data to memory device 64. Electrical contacts 104 provide asliding electrical contact with the corresponding contacts within outerhousing 46. Outer section 100 extends outward beyond the outer surfaceof inner housing 46 and provides a gripping surface that may be grippedto remove or install memory device 64.

Generally, the meter mechanism discussed herein include one or moreremovable memory device that includes operation mode information that isread by the electronic meter control system to select the operation modeof the meter mechanism. Referring to FIG. 10, a diagram of removablememory device 64 is shown according to an exemplary embodiment, andFIGS. 11 and 12 show a process of utilization of data from memory device64 by a new meter mechanism 44 to configure new meter mechanism 44 tooperate properly within parking system 10. As shown in FIG. 10, memorydevice 64 may include location identification information, shown as alocation ID 130, that uniquely identifies an individual single spacemeter 12 and/or that identifies an individual outer housing 42 withinparking system 10. In one embodiment, location ID 130 is a uniqueidentifier identifying the physical, geographic location within parkingsystem 10 of the single space meter outer housing 42 in which memorydevice 64 is located. Location ID 130 may be direct location data (e.g.,coordinates, address, etc.), and in other embodiments, location ID 130may be an identifier that may be cross-referenced to identify thelocation of an individual single space meter 12. Location ID 130 is anexample of operation mode information because identification of locationID on memory device 64 indicates that the meter re-assignment processshown in FIGS. 11 and 12 is to occur. Memory device 64 may also includepayment information, shown as audit data 132. Audit data 132 is datarepresentative of currency that has been received by the single spacemeter and that should be located in the currency box of the meter. Auditdata 132 from a particular single space meter is a variable data set anddepends on the amount of currency that has been applied to the metersince the last time the currency box had been emptied. Paymentinformation stored on memory device 64 may also include batched creditcard transaction data.

Memory device 64 includes rate data 134. Rate data 134 is datarepresentative of the cost of parking at single space meter 12. Invarious embodiments, rate data 134 provides a cost per unit time (e.g.,cost per quarter hour, cost per hour, etc.) and may be variable. Forexample, variable rate data 134 for a particular meter may include dataindicating that the parking rate increases during times of peak usageand decreases during times of lower use. Memory device 64 also includesmeter configuration information, shown as meter operation data andinstructions 136. Meter operation data and instructions 136 include dataand/or software that can be accessed by the meter mechanism 44 to ensuremeter mechanism 44 operates properly. In various embodiments, meteroperation data and instructions 136 includes operation software that isused by meter controller 50 to control the various devices of metermechanism 44. In one embodiment, data and instructions 136 areinstructions utilized by controller 50 to control display 54. In such anembodiment, data and instructions 136 may be specific to a particularcity or location in that data and instructions 136 are configured toallow meter to display a customized message (e.g., a city's name, a nameof an area or shopping district, etc.).

Removable memory 64 also includes owner data, shown as city code 138 andcustomer code 139. City code 138 is a unique identifier that identifiesthe city that the parking meter belongs to. As discussed in more detailbelow, city code 138 is utilized to ensure that a particular metermechanism is used and installed in a meter owned by the correct city.Customer code 139 is a unique identifier that identifies theowner/operator of parking system 10 within parking management system 18(specifically within the database maintained by server 19). Customercode 139 is used to ensure data from single space meter 12 is associatedwith the correct customer within parking management system 18. Furtheruses of a unique identifier for a customer allows parking managementsystem 18 to manage multiple parking systems 10 each having their ownunique customer ID.

While installed and operating at a single space meter 12, the controlsystem 50 of meter mechanism 44 is configured to update the informationstored on removable memory device 64 so that it is up to date. Forexample, as meter mechanism 44 receives payment, audit data 132 isupdated on memory device 64. As meter mechanism receives updates to therate schedule or to various configuration data and software (e.g., viaautomatic wireless update from parking management system 18), rate data134 and meter operation data and instructions 136 are updated.

As noted above, removable memory device 64 is configured to facilitatereplacement of a first electronic meter mechanism 44 (e.g., a currentmeter mechanism, a pre-existing meter mechanism, etc.) with a secondelectronic meter mechanism 44 (e.g., a replacement meter mechanism, anew meter mechanism, etc.). FIG. 11 depicts a process for replacing apre-existing electronic meter mechanism 44 with a new electronic metermechanism 44 according to an exemplary embodiment. At step 110, outermeter housing 42 is opened. Outer meter housing 42 is the housing of aparticular single space meter 12 located at a physical, geographiclocation with parking system 10. At step 112, the pre-existingelectronic meter mechanism 44 is removed from outer meter housing 42.The pre-existing electronic meter mechanism 44 is a meter mechanism thathas been operating at a particular single space meter 12 previously thatmay need to be replaced for a variety of reasons including failure ofone or more of the mechanism components, need for routine maintenance,replacement with upgraded meter mechanism version, etc.

At step 114, a new electronic meter mechanism 44 is provided. In oneembodiment, at step 114, providing the new electronic meter mechanism 44includes delivering the new electronic meter mechanism to a recipient.In this embodiment, it may be the recipient (e.g., an employee, aco-worker, a third-party purchaser, a customer, a customer's employee,etc.), that performs or operates the meter mechanism to perform theother steps shown in FIGS. 11 and 12. At step 116, removable memorydevice 64 is removed from the pre-existing electronic meter mechanism44, and at step 118, the removable memory device 64 from thepre-existing electronic meter mechanism 44 is inserted into slot 80 ofthe new electronic meter mechanism 44. At step 120, control system 50 ofthe new meter mechanism accesses data on removable memory device 64, andcontrol system 50 utilizes the data from removable memory device 64 toensure that new meter mechanism 44 is configured to operate properly forthe geographic location of parking meter 12 and to operate properlywithin parking system 10. In one embodiment, electronic meter mechanism44 includes a reset button that when pressed instructs the metermechanism to access the data on removable memory device 64. Becausememory device 64 includes the same rate data, configuration data andpayment data as the pre-existing meter mechanism 44, transferring thisinformation from memory device 64 directly to the new meter mechanismensures that the new meter mechanism 44 operates the same as thepre-existing meter mechanism 44.

FIG. 12 shows a process of utilization of data from the memory device 64of the pre-existing meter mechanism 44 by the new meter mechanism 44 toconfigure new meter mechanism 44 to operate properly within parkingsystem 10. At step 140, when instructed to access data from removablememory device 64 (e.g., by pressing of the meter reset button asdiscussed above), meter control system 50 first checks to make surememory device 64 and the new meter mechanism 44 are assigned to the samecity. In one embodiment, confirmation at step 140 occurs by comparing acity code stored on the permanent memory on the new meter mechanism 44with city code 138 on memory device 64. If the city codes match, itindicates that both the memory device 64 and the new meter mechanism 44are assigned to the same city, and the process proceeds. If the citycodes do not match, an error code is displayed on screen 54 indicatingthat city codes do not match.

At step 142, meter control system 50 determines the type of removablememory device present. In one embodiment, control system 50 maydetermine that memory device 64 is from the pre-existing meter byidentifying location ID 130. In this embodiment, identification oflocation ID 130 provides the indication to meter control system 50 thatmeter mechanism replacement is occurring and indicates that metercontrol system 50 should perform the meter mechanism replacement processshown in FIG. 12. If a location ID 130 is not present, meter controlsystem 50 utilizes the memory device in one of the modes or processesdiscussed below or will generate an error message.

As shown in FIG. 12, information from memory device 64 is directlytransferred to the new meter mechanism 44. Specifically, at step 144,location ID 130, audit data 132, rate data 134 and meter operation dataand instructions 136 are stored on the new meter mechanism 44. With thistransfer of information, new meter mechanism 44 includes all of the dataand software to ensure new meter mechanism 44 operates properly in placeof the previous meter mechanism 44. For example, audit data 132 iscarried over to the new meter so that as additional payments arereceived by the parking meter the audit data 132 includes an accuratetotal despite the replacement of the meter mechanism. Rate data 134 isused to ensure the new meter mechanism 44 adds the appropriate amount oftime to the meter upon receipt of payment. Meter operation data andinstructions 136 are used by the new meter mechanism 44 to ensure properoperation of the devices controlled by meter control system 50.

At step 146, unique meter mechanism ID information, for example theserial number that identifies the new meter mechanism 44 is communicatedto server 19 of parking management system 18. The database maintained byserver 19 is then updated such that the new meter mechanism serialnumber is associated with location ID 130 on the server. In this way,parking management system 18 is able to track the physical, geographiclocation of each unique meter mechanism 44 within parking system 10. Inone embodiment, the unique customer ID 139 from memory device 64 iscompared with the customer ID associated with the location ID and meterserial number on server 19 to ensure that the new meter mechanism islinked to the database for the appropriate customer. In one embodiment,control system 50 controls communication subsystem 52 to wirelesslycommunicate the new serial number to parking management system 18 viawireless network 16. Because meter mechanism 44 is able to communicatedirectly with parking management system 18, meter mechanism 44 is ableto perform the serial number update without further technicianinvolvement. In one embodiment, a unique meter ID number is generatedbased on the meter serial number and the meter ID number is used toproperly correlate data within the database of server 19.

Generally, as new meter mechanism 44 configures itself to operateproperly for a particular single space meter 12, meter mechanism 44utilizes its wireless communication functions to synchronize variousdata and software with parking management system 18. At step 148,control system 50 controls communication subsystem 52 to wirelesslyreceive updated real-time clock data from parking management system 18.Control system 50 then uses the real-time clock data to update localtime keeping process as needed. This helps ensure proper time-keeping bynew meter mechanism 44.

At step 150, a check is performed to ensure that the rate data 134 andmeter operation data and instructions 136 received from removable memorydevice 64 are up to date. For example, the database maintained by server19 includes rate data and configuration data associated with each uniquelocation ID. If the rate data 134 and/or meter operation data andinstructions 136 stored on the new meter mechanism 44 do not match thecorresponding data maintained by server 19 for the unique location ID,it is determined that an update is needed. If an update is needed, newversions of rate data 134 and/or operation data and instructions 136 aredownloaded wirelessly from parking management system 18 utilizingcommunications subsystem 52 of the new meter mechanism 44. Because metermechanism 44 is equipped with wireless communications hardware thatallows it to communicate directly with server 19, meter mechanism 44 canautomatically synchronize files that were out of date on the prior metermechanism 44.

It should be understood that removable memory device 64 provides amechanism by which the current data maintained by a pre-existing metermechanism 44 may be directly transferred to a replacement metermechanism 44. In other embodiments, other direct transfers of the datashown on memory device 64 may be used. For example, in one embodimentduring the replacement process, a cable may be connected from thepre-existing meter mechanism 44 to the new meter mechanism 44, and theneeded data is transferred directly from the non-volatile memory of thepre-existing meter mechanism 44 to the non-volatile memory of the newmeter mechanism 44. In another embodiment, this transfer may occur viadirect short range, wireless communication link (e.g., a blue toothlink). In these embodiments, the needed data is transferred directlyfrom one meter to a new meter without the need for an intermediatedevice (e.g., a laptop, a handheld computer, etc.) receiving the datafirst. Further, direct transmission of data from the old meter to thenew meter, particularly data generated locally by the meter (e.g.,payment data, vehicle sensor data, etc.), allows for integrity of datain the event of communications failure between the pre-existing meterand parking management system 18.

In various embodiments, the ability to read a removable memory device,such as removable memory device 64, may be utilized during processesother than the meter mechanism replacement process discussed above. Forexample as shown in FIG. 13, a removable memory device 160 can beconfigured to place a meter mechanism 44 into a diagnostics/maintenancemode. Memory device 160 includes a diagnostics ID 162 instead oflocation ID 130. Diagnostics ID 162 is an example of operation modeinformation because identification of diagnostics ID 162 on memorydevice 160 indicates that the meter diagnostic process shown in FIG. 14should occur. Diagnostics ID 162 is read by meter mechanism 44 andtriggers start of the diagnostics/maintenance mode. Memory device 160also includes diagnostics data and instructions 164 that are utilized bymeter mechanism 44 to operate in the diagnostics/maintenance mode.Memory device 160 includes a diagnostic database ID 166 instead of ownerID information (e.g., city code 138 or the customer ID 139 discussedabove). Diagnostic database ID 166 puts meter mechanism 44 incommunication with a diagnostics database located on server 19 to ensuredata generated by the meter mechanism during diagnostics does not getcommunicated to a “live” customer database located on server 19.

Referring to FIG. 14, a method of performing diagnostics and maintenancefor a meter mechanism 44 is shown according to an exemplary embodiment.At step 170, a diagnostics/maintenance memory device 160 is insertedinto memory slot 80 of the meter mechanism. At step 172, the metermechanism is instructed to read memory device 160, for example bypressing the reset button. At step 174, meter mechanism 44 readsdiagnostic ID 162 of memory device 160 and determines that thediagnostic/maintenance mode should be entered.

At step 176, the diagnostics data and instructions 164 are utilized bymeter mechanism 44 to ensure proper operation of the mechanism duringthe diagnostics and maintenance process. For example, diagnostics dataand instructions 164 include instructions to provide for proper displayof diagnostics information and menus on display 54 of the metermechanism. Diagnostics data and instructions 164 may also include testdata (e.g., test audit data, test rate data, test time data, test errorcodes, etc.) that may be utilized during the maintenance process toconfirm proper operation of the meter mechanism 44. At step 178, metermechanism 44 is linked to a diagnostics database associated with parkingmanagement system 18. In one embodiment, the diagnostics database ID 166is read by meter mechanism 44, and meter mechanism 44 controls wirelesscommunications subsystem 52 to transmit diagnostics database ID 166 toparking management system 18 via wireless network 16. Use of diagnosticsdatabase ID 166 links meter mechanism 44 to a diagnostics database thatis part of parking management system 18. This link ensures that datatransmitted wirelessly from meter mechanism 44 during diagnostics andmaintenance is not stored in a live customer database.

In another embodiment, memory device 160 may include a diagnostic dataflag in place of, or in addition to, diagnostics database ID 166. Inthis embodiment, during diagnostic mode, meter mechanism 44 may beconfigured to transmit data generated during diagnostics directly to alive customer database, and in this embodiment, the diagnostic data isstored in the live database associated with the diagnostic data flag.The diagnostic data flag provides an indicator that can be used toidentify and segregate the diagnostic data from real data in the liveparking database. In this embodiment, server 19 may be configured tohandle parking data associated with the diagnostics data flag in variousways. For example, in one embodiment, following diagnostics, server 19may be configured to search and delete all data associated with adiagnostic data flag. Further the diagnostics data flag may be used byserver 19 to store and/or display diagnostics data in a separatediagnostics data table, and server 19 may be configured to performvarious server-side diagnostics procedures using the flagged diagnosticsdata.

Referring to FIG. 15, a removable memory device 180 configured to placea meter mechanism 44 into a low power standby mode and to assign themeter to “spare” status is shown. Memory device 180 includes a standbyor “spare” meter ID 182, spare meter operation instructions 184, city ID186 and customer ID 188. Generally, spare meter ID 182 takes the placeof location ID and is utilized by the meter mechanism 44 to identifythat the meter mechanism 44 is being assigned as a spare. Spare meter ID182 is an example of operation mode information because identificationof spare meter ID 182 on memory device 180 indicates that the process ofplacing the meter mechanism is the low power standby mode, shown in FIG.16, should occur. Spare meter operation instructions 184 are utilized bymeter mechanism 44 to ensure meter mechanism 44 operates properly in thelow power standby mode while the mechanism is assigned as a spare. CityID 186 and customer ID 188 are utilized to properly update the databasefor the proper city and customer to identify that the particular metermechanism is assigned as a spare instead of being assigned to aparticular single space meter 12 in parking system 10.

Referring to FIG. 16, a process for configuring a meter mechanism 44 asa spare is shown according to an exemplary embodiment. At step 190,memory device 180 is inserted into slot 80 of a meter mechanism 44. Atstep 192, meter mechanism 44 is instructed to access memory device 180for example by the pressing of the reset button. At step 194, metercontrol system 50 first checks to make sure memory device 180 and thenew meter mechanism 44 are assigned to the same city. In one embodiment,this confirmation occurs by comparing a city code stored on thepermanent memory on the new meter mechanism 44 with city code 186 onmemory device 180. If the city codes match, it indicates that both thememory device 180 and the new meter mechanism 44 are assigned to thesame city, and the process proceeds. If the city codes do not match, anerror code is displayed on screen 54 indicating that city codes do notmatch.

At step 196, the database maintained by server 19 is updated to showthat the particular meter mechanism 44 used by the city is assigned as a“spare” and is no longer associated with a particular location ID. Atstep 196, customer ID 188 may be checked to ensure that the appropriatecity's database is being updated. In one specific embodiment, thedatabase entry for a particular meter (e.g., indexed using the meterserial number or other unique meter identifier) is updated to set thelocation ID for that particular meter to a value indicating spare status(e.g., a null value). In another embodiment, a spare location ID may beset showing the physical location of a spare meter within a city'sstorage facilities. In another embodiment, the database record for aparticular meter may have a field identifying whether a meter is a spareor not. Communication to update the meter mechanism's status as a spareoccurs utilizing the wireless communication subsystem 52 of metermechanism 44.

Following updating of the database at step 196, at step 198, controlsystem 50 of meter mechanism 44 utilizes spare meter configuration dataand instructions 184 to enter the low power standby operation mode. Inone embodiment, during standby mode, display screen 54 displays anappropriate message, for example “standby” or “spare.” In anotherembodiment, display screen 54 is turned off to conserve power. Inaddition, various components of meter mechanism 44 may be powered downor inactivated to conserve power during standby mode. In one suchembodiment, meter mechanism 44 is configured to cease wirelesscommunication via communication subsystem 52 when in standby mode. Inaddition, periodic polling of currency or payment sensors in the paymentreceiving devices of meter mechanism 44 is ceased. In this mode, thespare meter mechanism may be stored until needed while using minimalpower from the meter's battery. A meter that has been assigned “spare”status may be reassigned to active status by the insertion of a memorydevice, such as memory device 64, associated with a particular physicalmeter location within parking system 10. The process shown in FIG. 11and FIG. 12 may then be executed to move meter mechanism 44 from “spare”status to active status.

Referring to FIG. 17, a removable memory device 300 configured tofacilitate extraction of various data from a meter mechanism 44 is shownaccording to an exemplary embodiment. Memory device 300 includes a dataextraction ID 302 and a storage location, shown as available memory 304.Memory device 300 also includes a city ID 306. Data extraction ID 302 isan example of operation mode information because identification of dataextraction ID 302 on memory device 300 indicates that the dataextraction process shown in FIG. 18 should occur.

Meter mechanism 44 is configured to store various information duringoperation of the meter mechanism at one of the single space meters 12within parking system 10 as discussed above. For example, metermechanism 44 includes a non-volatile memory that stores audit data(e.g., audit data 132 shown above) regarding the amount of currency thathas been received by the meter. Meter mechanism 44 also stores batchedcredit card transaction data (e.g., data regarding credit cardtransactions that are stored for processing at a later time, typicallybecause real-time credit card authorization was not available at thetime of credit card payment). Meter mechanism 44 may also includestorage of various logs, information from the vehicle sensor associatedwith the single space meter, error codes, data regarding power usage,etc. Removable memory device 300 is configured for extraction of suchdata prior to operations in which such data may be erased or theintegrity of the data may be compromised.

Referring to FIG. 18, a data extraction process using memory device 300is shown according to an exemplary embodiment. At step 310, memorydevice 300 is inserted into slot 80 of a meter mechanism 44. At step312, meter mechanism 44 is instructed to access memory device 300, forexample, by the pressing of the reset button. At step 314, meter controlsystem 50 first checks to make sure memory device 300 and the new metermechanism 44 are assigned to the same city. In one embodiment, thisconfirmation occurs by comparing a city code stored on the permanentmemory on the new meter mechanism 44 with city code 306 on memory device300. If the city codes match, it indicates that both the memory device300 and the new meter mechanism 44 are assigned to the same city, andthe process proceeds. If the city codes do not match, an error code isdisplayed on screen 54 indicating that city codes do not match.

At step 316, local data from meter mechanism 44 is stored to availablememory 304 of memory device 300. The user or technician can then use thedata as needed. For example, logged data can be stored within thedatabase of server 19 for the particular meter, and batched credit cardtransactions can be processed. If no local data is present on metermechanism 44, in one embodiment a message is displayed on screen 54indicating that there is no data to extract. In various embodiments, thedata extraction process shown in FIG. 18 may be performed prior to anyprocess in which loss of locally stored data may occur. For example, thedata extraction process shown in FIG. 18 may be performed prior toreassignment using memory device 64, prior to diagnostics andmaintenance using memory device 160 and prior to assignment as a spareusing memory device 180.

In one embodiment, a parking meter kit is provided. In this embodiment,the kit includes one or more electronic meter mechanisms 44, one or moreremovable memory devices 64 configured to facilitate replacement of onemeter mechanism of a single space meter with a new electronic metermechanism, one or more diagnostics memory devices 160, one or more sparememory devices 180 and/or one or more data extraction memory devices300.

Referring to FIG. 19, a block diagram of electronic meter mechanism 44is shown according to an exemplary embodiment. In this embodiment,electronic meter mechanism 44 includes two distinct processors, shown asperipheral device and communication controller 200 and single-spacemeter (SSM) controller 202, and the local processing and controlfunctions of electronic meter mechanism 44 are divided between the twoprocessors. Generally, SSM controller 202 conducts the processing forand controls the display 204, a user input device, such as keypad 216 orinput device 58 shown in FIG. 7, and the time-keeping functions of themeter (e.g., determining current time remaining on the meter, decreasingtime remaining as time passes, increasing time remaining as payment ismade, determining expiration of the meter when time expires, etc.), andcommunication controller 200 conducts processing for and controlswireless communication subsystem 210, vehicle sensor 214 and memorydevice reader 250. In addition, control of the additional components ofelectronic meter mechanism 44 may be split between the two processors200 and 202 as shown below in FIG. 19.

In one embodiment, both controllers 200 and 202 are controllersspecifically configured for control of certain components of anelectronic meter mechanism. In another embodiment, controller 200 is amulti-purpose or multi-use control/communication device that iscommunicably coupled a dedicated single-space meter controller 202 inorder to supplement the functionality provided by SSM controller 202 andto equip electronic meter mechanism 44 with additional peripheraldevices that are not controlled by SSM controller 202. For example, inone embodiment, SSM controller 202 is a dedicated single-space metercontroller and is coupled to, interfaces and/or controls a user display204, a money sensor 206, a smart card reader 208 and keypad 216. In onespecific embodiment, SSM controller 202 is the controller present in aconventional electronic single-space parking meter and controller 200 iscommunicably coupled to SSM controller 202 along with additionalcomponents shown in FIG. 19 (e.g., elements 210, 212, 214, 218 and 250)as a retrofit unit to provide additional functionality to the meter. Thedivision of control between two processors may provide electronic metermechanism 44 with a higher efficiency and lower power requirement, thanif one single processor were used. For example, both controllers 200 and202 have a low power state and a high power state, and the controllersare configured to be in a low power state when the devices it controlsare not active and in the high power state when the devices under itscontrol are active. For example, controller 202 may transition from thelow power to the high power state when data is to be received ortransmitted using the wireless communications hardware.

SSM controller 202 controls display of information on display 204 andalso receives and processes input signals received from keypad 216. SSMcontroller 202 is configured to receive information from keypad 216. SSMcontroller 202 may use this data to alter the display of information ondisplay 204 based on the user inputs and to operate the payment receiptfunctions of the meter. As shown in FIG. 5, keypad 216 may be a fourbutton keypad that allows the user to operate the parking meter. In thisembodiment, SSM controller 202 may communicate information received fromkeypad 216 to controller 200, and controller 200 may in turn communicatethe information to parking management system 18 via wirelesscommunication subsystem 210.

SSM controller 202 receives an input signal from money sensor 206indicating when a user has placed money into the parking meter. Moneysensor 206 may include an inductive coil sensor configured to detectthat presence and denomination of coin placed in the coin slot of themeter. In another embodiment, money sensor 206 may be an optical sensorassociated with a coin slot configured to detect the presence and thedenomination of coins placed in the coin slot of the meter. In oneembodiment, money sensor 206 may incorporate an inductive coin sensor todetect money entering the coin slot and an optical sensor to detect ajam or foreign object located within the coin slot. Money sensor 206 mayalso include an optical sensor associated with a paper money slotconfigured to detect the presence and the denomination of paper moneyplaced into the paper money slot of the meter. SSM controller 202 alsoreceives input from smart card reader 208 indicating that the user haspaid for parking using a smart card.

Peripheral device and communication controller 200 may be communicablycoupled to a variety of additional parking meter devices to supplementthe functionality provided by SSM controller 202. In the embodimentshown in FIG. 19, controller 200 is coupled to, interfaces and/orcontrols a wireless communication subsystem 210, a power supply system212, a vehicle sensor 214, a credit card reader 218 and a removablememory device reader 250. Thus, with controller 200 coupled to SSMcontroller 202, electronic meter mechanism 44 is provided with thefunctionalities provided by wireless communication subsystem 210, powersupply system 212, vehicle sensor 214, user interface keypad 216, creditcard reader 218 and memory device reader 250.

Controller 200 controls wireless communication subsystem 210 to provideelectronic meter mechanism 44 with wireless communication functionality.As discussed in detail above, wireless communication subsystem 210provides the communication hardware and software that allows metermechanism 44 to send information to and to receive information fromparking management system 18. Signals indicating that payment has beenreceived from money sensor 206 or smart card reader 208 may becommunicated from SSM controller 202 to controller 200, and controller200 may in turn communicate this information to parking managementsystem 18 utilizing wireless communication subsystem 210. Further,controller 200 may communicate information received from power supply212, vehicle sensor 214 and credit card reader 218 to parking managementsystem 18 using wireless communication subsystem 210. In one specificembodiment, controller 200 may communicate data to the SSM controller202 that indicates the receipt of a credit card payment has beenreceived, and SSM controller 202 is configured to add time to the meterand to display additional time based upon the data related to thereceipt of credit card payment.

As discussed above, wireless communication subsystem 210 may includehardware and software to communicate directly with parking managementsystem 18 via cellular telephone communication standards. In otherembodiments, wireless communication subsystem 210 may utilize an RFbased communication standard to communicate with a gateway which in turncommunicates with parking management system 18.

Controller 200 interfaces with power supply 212 to provide power to thecomponents of electronic meter mechanism 44. As shown in FIG. 19, powersupply 212 includes a rechargeable battery 220 and one or more solarcells or solar panels 222 (e.g., front solar panel 90 and/or rear solarpanel 91). Battery 220 may be one or multiple batteries and may powerboth controller 200 and SSM controller 202 and the components coupled toeach controller. Solar panel 222 is coupled to battery 220 and acts torecharge battery 220. Solar panel 222 is physically located on thehousing of meter mechanism 44 such that it may receive sunlighttransmitted through the window located on the front and or rear surfacesof the outer housing of the meter. Controller 200 may receive datarelated to various operating states of power supply 212 and maycommunicate this data to parking management system 18 via wirelesscommunication subsystem 210. For example, controller 200 may receivedata regarding the charge state of battery 220, recharge rate of battery220, the recharge effectiveness or efficiency of solar cell 222, etc.This data may be processed by parking management system 18 to determinewhether a battery and/or solar cell in a particular single-space meterneeds to be replaced.

Controller 200 also interfaces vehicle sensor 214. Vehicle sensor 214may be pole-mount vehicle sensors 20, curb surface-mount sensor 22 orstreet surface-mount sensor 24 discussed above, or any other sensingdevice suitable for vehicle detection of the past, present or future.Vehicle sensor 214 generates a signal indicative of the vehicle locatedin the parking spot associated with electronic meter mechanism 44 andcommunicates the signal to controller 200. Controller 200 maycommunicate information related to the vehicle in the parking space toSSM controller 202, and SSM controller 202 may use this information tooperate the devices under its control. For example, display 204 may beupdated by SSM controller 202 based on the information from vehiclesensor 214 to prompt the user of the parking meter to select the methodof payment to be used for the parking session. Controller 200 may alsotransmit data from vehicle sensor 214 to parking management system 18using wireless communication subsystem 210. In one embodiment, processor200 is configured to process the signal indicative of the presence ofthe vehicle within the parking space received from vehicle sensor 214 todetermine whether a vehicle is parked in the parking space when themeter is expired. In this embodiment, processor 200 is configured tocontrol wireless communication subsystem 210 to transmit data indicativeof a vehicle parked at an expired meter to parking management system 18.

Controller 200 also interfaces with a credit card reader 218 configuredto generate a signal indicative of credit card data of the credit cardreceived by the reader. Credit card reader 218 includes a card detector224 and a mag-strip reader 226. Card detector 224 detects the presenceof a credit card being inserted into the slot of the credit card readerand information indicative of the presence of a credit card iscommunicated to controller 200. Controller 200 may communicate thisinformation to SSM controller 202, and SSM controller 202 may updatedisplay 204 to indicate that payment by credit card is being used.

Controller 200 and/or SSM controller 202 may be configured to execute afunction that allows the user to pay for parking using the credit card.Mag-strip reader 226 reads the credit card information from the user'scredit card. The credit card information is communicated from mag-stripreader 226 to controller 200, and controller 200 communicates thisinformation to a credit card authorization system using wirelesscommunication subsystem 210 for authorization and processing. The creditcard authorization system processes the credit card information, andapproval information from the credit card authorization system isreceived by wireless communication subsystem 210 and is communicated tocontroller 200. If the payment by credit card is approved, controller200 communicates credit card approval to SSM controller 202, and SSMcontroller 202 updates display 204 and adds time to the meter asappropriate. If payment by credit card is not approved, controller 200communicates lack of credit card approval to SSM controller 202, and SSMcontroller 202 updates display 204 with the appropriate message and timeis not added to the meter.

Controller 200 is also communicably coupled to memory device reader 250.When one of the memory devices (e.g., memory device 64, memory device160, memory device 180 or memory device 300) discussed herein isreceived within slot 80, the electrical contacts of the memory deviceengage corresponding electrical contacts 252 of the memory devicereader. The contacts may provide for slidable and non-permanentelectrical interface between the removable memory device and the memorydevice reader. With one of the memory devices engaged with memory devicereader 250, controller 200 is able to communicate with the removablememory device to provide the various functionalities discussed herein.

As shown in FIG. 19, communication between the various components ofelectronic meter mechanism 44 is provided by communication links 246.Communication links 246 may be dedicated wires or wireless communicationconnections. Communication links 246 may also represent communicationover a network. Communication links 246 may be communication linksprovided on a printed circuit board, an integrated circuit or may becable connections. One or more communication links 246 may utilizevarious standard cable connections (e.g., Ethernet, USB, RJ-11, etc.),and one or more communication links 246 may utilize custom orproprietary cable connections. In one embodiment, communication links246 may be hardwired connections or couplings that allow forcommunication of data and also for the transmission of power from thepower supply to the various device of the meter mechanism. In variousembodiments, communication links 246 may be any combination of the typesof links discussed herein.

In one embodiment, a new electronic meter mechanism 44 may beconstructed utilizing a first controller 200 to control a first group ofperipherals (e.g., devices 210, 212, 214, 218 and 250) and a secondcontroller 202 to control a second group of peripherals (e.g., devices204, 206, 208 and 216). In other embodiments, an existing electronicmeter mechanism 44 having an SSM meter controller 202 that controls apre-existing group of peripherals (e.g., devices 204-208 and 216) isupgraded by the addition of controller 200 and a new group ofperipherals (e.g., devices 210, 212, 214, 218 and 250). In thisembodiment, controller 200 may be physically present on a separate boardor chip than controller 202, and controller 200 may be coupled tocommunicate with controller 202 to provide electronic meter mechanism 44with the functions provided by the new group of peripherals. In anotherembodiment, the functionality of controller 200 and SSM controller 202may be provided by a single controller (e.g., a single processingcircuit including hardware and software to control devices 204-208 and210-218 and 250).

In one embodiment, display 204 may be an upgraded display (e.g., a colordisplay, high resolution display, graphical display, etc.) that is partof a retrofit unit. In one such embodiment, controller 200 (instead ofSSM controller 202) may control the display of information via display204 in order to provide updated software, processing power, etc. neededto control upgraded display 204. In this embodiment, the display controlfunctionality of SSM controller 202 may be disabled and SSM controller202 may only control devices 206, 208 and 216.

Referring to FIG. 20, a detailed block diagram of peripheral device andcommunication controller 200 is shown according to an exemplaryembodiment. Controller 200 may generally be an electronic control unitsuitable to provide electronic meter mechanism 44 with the variousfunctionalities described herein. For example, controller 200 may be anembedded system, a dedicated circuit, a general purpose system orcircuit programmed with the functionality described herein, etc.Controller 200 includes a processing circuit 230, memory 232, acommunication module and interface 234, a single-space meter module 236,a vehicle sensor module 238, a power supply module 240, a credit cardreader module 242 and memory device module 248. In one embodiment,controller 200 may include a user input module 244, which may bedisabled in applications in which the user input device is controlled bySSM controller 202.

Processing circuit 230 may be a general purpose processor, anapplication specific processor (ASIC), a circuit containing one or moreprocessing components, a group of distributed processing components, agroup of distributed computers configured for processing, etc.,configured to provide the functionality of module components ofcontroller 200. Memory 232 (e.g., memory unit, memory device, storagedevice, etc.) may be one or more devices for storing data and/orcomputer code for completing and/or facilitating the various processesdescribed in the present disclosure. Memory 232 may include volatilememory and/or non-volatile memory. Memory 232 may include databasecomponents, object code components, script components, and/or any othertype of information structure for supporting the various activitiesdescribed in the present disclosure.

According to an exemplary embodiment, any distributed and/or localmemory device of the past, present, or future may be utilized with thesystems and methods of this disclosure. According to an exemplaryembodiment, memory 232 is communicably connected to processing circuit230 and module components 234-244 and 248 (e.g., via a circuit or anyother wired, wireless, or network connection) and includes computer codefor executing one or more processes described herein. A single memoryunit may include a variety of individual memory devices, chips, disks,and/or other storage structures or systems.

Module components 234-244 and 248 may be computer code (e.g., objectcode, program code, compiled code, script code, executable code,instructions, programmed instructions, non-transitory programmedinstructions, or any combination thereof), hardware, software, or anycombination thereof, for conducting each module's respective functions.Module components 234-244 and 248 may be stored in memory 232, or in oneor more local, distributed, and/or remote memory units configured to bein communication with processing circuit 230 or another suitableprocessing system.

Communication module and interface 234 includes one or more componentsfor communicably coupling controller 200 to the other components ofparking system 10. For example, in the embodiment shown in FIG. 19,communication module and interface 234 includes one or more componentsfor communicably coupling controller 200 to the other components ofelectronic meter mechanism 44 via communication links 246. As discussedin more detail below, communication module and interface 234 includesone or more components for communicably coupling controller 200 tovarious components of parking system 10 in various differentconfigurations.

Communication module and interface 234 may include one or more jacks orother hardware for physically coupling communication links 246 tocontroller 200, analog to digital converters, digital to analogconverters, signal processing circuitry, and/or other suitablecomponents. Communication module and interface 234 may include hardwareconfigured to connect controller 200 with the other components ofelectronic meter mechanism 44 via wireless connections. Communicationmodule and interface 234 is configured to support the communicationactivities of controller 200 (e.g., negotiating connections,communication via standard or proprietary protocols, etc.).Communication module and interface 234 is also configured to supportoperation of wireless communication subsystem 210 to provideconnectivity and communication between controller 200 and parkingmanagement system 18 via a wired or wireless network.

Single-space meter module 236 is configured to allow controller 200 tointerface and communicate data with one or more SSM controllers 202.Vehicle sensor module 238 is configured to allow controller 200 tointerface with, communicate data with and/or control one or more vehiclesensors 214. Power supply module 240 is configured to allow controller200 to interface with, communicate data with and/or control power supply212. Power supply module 240 may also be configured to regulate anddistribute power from power supply 212 to power various components ofcontroller 200, or other components of parking system 10 as needed in aparticular arrangement. Credit card reader module 242 is configured toallow controller 200 to interface with, communicate data with and/orcontrol credit card reader 218. Credit card reader module 242 is alsoconfigured to allow controller 200 to interface with a credit cardauthorization system to process credit card payments. User input module244 is configured to allow controller 200 to interface with, communicatedata with and/or control keypad 216. Memory device module 248 isconfigured to allow controller 200 to interface and to read and writedata to a removable memory device received within memory device reader250.

Further modifications and alternative embodiments of various aspects ofthe invention will be apparent to those skilled in the art in view ofthis description. Accordingly, this description is to be construed asillustrative only. The construction and arrangements, shown in thevarious exemplary embodiments, are illustrative only. While the currentapplication recites particular combinations of features in the variousembodiments discussed herein, various embodiments of the inventionrelate to any combination of any of the features described herein, andany such combination of features may be claimed in this or futureapplications. Any of the features, elements, or components of any of theexemplary embodiments discussed above may be claimed alone or incombination with any of the features, elements, or components of any ofthe other embodiments discussed above.

Although only a few embodiments have been described in detail in thisdisclosure, many modifications are possible (e.g., variations in sizes,dimensions, structures, shapes and proportions of the various elements,values of parameters, mounting arrangements, use of materials, colors,orientations, etc.) without materially departing from the novelteachings and advantages of the subject matter described herein. Someelements shown as integrally formed may be constructed of multiple partsor elements, the position of elements may be reversed or otherwisevaried, and the nature or number of discrete elements or positions maybe altered or varied. The order or sequence of any process, logicalalgorithm, or method steps may be varied or re-sequenced according toalternative embodiments. Other substitutions, modifications, changes andomissions may also be made in the design, operating conditions andarrangement of the various exemplary embodiments without departing fromthe scope of the present invention.

What is claimed is:
 1. A single space electronic parking meter mechanismfor inserting into an outer parking meter housing comprising: an innerhousing; a payment receiving structure supported by the inner housing;an electronic display screen supported by the inner housing; a wirelesscommunication subsystem supported by the inner housing configured towirelessly communicate with a parking management system; an electronicmeter control system controlling the electronic display and the wirelesscommunications subsystem; a memory device receiving port externallyaccessible through the inner housing; and a read-write removable memorydevice physically accessible from outside of the inner housing andconfigured to be coupled to the memory device receiving port, theremovable memory device including operation mode information that isread by the electronic meter control system to select an operation modeof the meter mechanism.
 2. The single space electronic parking metermechanism of claim 1, wherein operation mode information includes:location ID information representative of the physical, geographiclocation of the outer parking meter housing; payment informationrepresentative of parking payments received by the payment receivingstructure; and meter configuration information utilized by the controlsystem to control operation of the display.
 3. The single spaceelectronic parking meter mechanism of claim 2, wherein the electronicmeter control system is configured to store the payment information, thelocation ID information and the meter configuration information to anon-volatile memory associated with the electronic meter mechanism. 4.The single space electronic parking meter mechanism of claim 2, whereinthe meter control system is configured to control the wirelesscommunication subsystem to communicate the location ID informationreceived from the removable memory device to the parking managementsystem.
 5. The single space electronic parking meter mechanism of claim2 wherein the payment receiving structure includes a currency reader anda credit-card reader and payment information includes at least one ofaudit data representative of currency received by the currency readerand batched credit card transaction data representative of credit cardpayment information received by the credit-card reader.
 6. The singlespace electronic parking meter mechanism of claim 2 wherein meterconfiguration information further includes parking rate data.
 7. Thesingle space electronic parking meter mechanism of claim 1 whereinoperation mode information includes a diagnostic mode ID that when readby the meter control system causes the meter mechanism to operate in adiagnostic mode, wherein upon reading the diagnostic mode ID the metercontrol system controls the wireless communications subsystem totransmit data to a diagnostic database maintained by the parkingmanagement system.
 8. The single space electronic parking metermechanism of claim 1 wherein operation mode information includes a sparemode ID that when read by the meter control system causes the metermechanism to operate in a low power standby mode.
 9. The single spaceelectronic parking meter mechanism of claim 1 wherein operation modeinformation includes a data extraction ID that when read by the metercontrol system causes the meter control system to save data to theremovable memory device.
 10. The single space electronic parking metermechanism of claim 9, wherein the data saved to the removable memorydevice includes batched credit card transaction data.
 11. The singlespace electronic parking meter mechanism of claim 1 comprising: a memorydevice reader having at least one electrical contact; wherein theremovable memory device includes at least one electrical contact forcoupling to electrical contact of the memory device reader when receivedwithin the memory device receiving port.
 12. A single space electronicparking meter mechanism configured for replacement of a current singlespace meter mechanism located within an outer parking meter housing, thesingle space electronic parking meter mechanism comprising: an innerhousing; a payment receiving structure supported by the inner housing;an electronic display screen supported by the inner housing; a wirelesscommunication subsystem supported by the inner housing configured towirelessly communicate with a parking management system; a non-removablememory device; a port extending through the inner housing and configuredto receive a removable memory device of the current single space metermechanism, the removable memory device including location identificationinformation representative of the physical, geographic location of thecurrent single space meter mechanism; and an electronic meter controlsystem controlling the electronic display and the wirelesscommunications subsystem; wherein the electronic meter control system isconfigured to access the location identification information from theremovable memory device, to copy the location identification data fromthe removable memory device to the non-removable memory device, and tocontrol the wireless communication subsystem to transmit the locationidentification information to the parking management system.